System for management and processing of electronic vendor mail

ABSTRACT

A computer-implemented system processes secure electronic documents from one or more content providers in accordance with subscriber instructions has a processor and modules operative within the processor. A monitoring module obtains a provider GUID, a subscriber GUID, and a transaction ID from public metadata associated with a transaction received from a particular content provider. A determination module determines any designees of the subscriber and contact information one or more of the subscriber and any designees. A transaction module distributes a transaction addressed to at least one of the subscriber and any designees. Each distributed transaction includes data that is used for management, tracking, and alerting. Also described is a station for constructing transactions for distribution to subscribers through such a system. An end-to-end system and method are described.

FIELD OF THE INVENTION

The present invention relates to improvements in commercial mail distribution and, more particularly, to a structured, secure and controlled electronic document distribution system to supplant at least a significant portion of existing physical mail distribution systems.

BACKGROUND OF THE INVENTION

In the past, distribution of commercial mail has depended on a large and complex process centered around the movement of paper. Paper needed to be delivered to the mail provider as raw material in the printing of documents. Paper also needed to be moved from the point of printing to the United States Postal Service (USPS) and within the USPS to a recipient destination. Even after delivery to the recipient, paper must be managed in order to reach the intended recipient or otherwise undergo an organization's processing requirements before ultimately being forwarded to long-term storage or disposal. These processes were necessary and reasonably efficient in a world where digital communication did not exist; however, the point of the process was never to move paper, but rather to move data. In today's electronic world it is entirely possible to reengineer the process to eliminate paper and remove the steps and costs associated with movement of physical mail.

The advent of email allows data to be quickly moved from one point to another without the need for paper or all of the requisite steps and costs of moving paper. The volume of email transacted daily has grown to quantities that are difficult to imagine. Nevertheless, current implementations of email do not adequately meet many of the requirements of commercial mail from either a provider or recipient standpoint. Email addresses may be transient and it is difficult to determine if any given address is either current or valid. Content within the body of an email is often unstructured and largely inconsistent. Email is relatively unsecure and can be intercepted more readily than physical mail as the later requires both the mail and the interceptor to be in the same place at the same time. Moreover, verification of normal email delivery is uncertain. Another complexity in traditional email management concerns the manner of organizing emails. Organization of email is at the discretion of the recipient, and management and processing of email messages are subject to the diligence of the user. Finally, if not appropriately backed up, email can be lost and irretrievable. As a direct result of these limitations, commercial providers have shied away from email as the primary form for distributing electronic versions of commercial mail.

Yet some commercial providers have begun utilizing “paperless” alternatives. This method eliminates the paper and the components of the legacy process that relate to moving physical paper. Unfortunately, however, the paperless alternatives available so far have been less desirable than paper-based delivery methods because they lack the passive receipt and aggregation components of both physical mail and email. The predominant paperless alternatives available today require a recipient to “follow a link,” sign-on to a provider website, and then open the required document. This approach prevents interception of personal or sensitive information. However, if the recipient fails to retrieve a document, he or she might miss a deadline. This is attendant with potential financial repercussions, legal implications, or both. As well, this process places additional time burdens on the recipient and can become particularly onerous if the recipient has to follow links to review materials relating to multiple commercial relationships.

A broad array of prior art exists around “Electronic Bill Presentment and Payment” systems. These systems are inherently different than other paperless systems in that they are focused on a singular type of document (an invoice) and tailored to process that one type of document. EBPP systems are directed to electronic payment and do not address non-payment related mail or many of the myriad consumer problems associated with document distribution, retention, and management.

Historically, replacements to physical mail distribution systems have been driven by providers who are motivated to lower the substantial costs associated with physical document distribution. Because the focus has been on the provider's cost, the complex requirements necessary to motivate recipients to convert away from physical document distribution have not been met. However, the current invention provides a system and method that, among other things, addresses the needs of recipients' while also lowering the costs associated with physical document distribution.

SUMMARY OF THE INVENTION

In accordance with a broad aspect of the invention, systems and methods are provided for secure end-to-end transmission of electronic documents from a content provider to a subscriber, in which a trusted intermediary manages, tracks and provides alerts concerning the flow of such documents. At one level, network participants access the system directly to register themselves and establish subscription relationships and rules. At another level, the system interacts on a computer-to-computer basis in an automated manner to validate, encode, encrypt, route, decrypt, organize and confirm delivery of individual document transactions.

In accordance with one aspect of the invention, a computer-implemented system processes secure electronic documents from one or more content providers in accordance with subscriber instructions. The system has a processor and a set of modules such as code that configure the processor or its host machine. A monitoring module is operative within the processor to obtain a provider GUID, a subscriber GUID, and a transaction ID from public metadata associated with a transaction received from a particular content provider. A determination module is operative within the processor to determine any designees of the subscriber and contact information of the subscriber and any designees. A transaction module is operative within the processor to construct a primary transaction addressed to the subscriber and including the transaction ID, and one or more supplemental transactions each addressed to any respective designees of the subscriber and each having a respective derivative transaction ID derived from the transaction ID.

In accordance with a further one aspect of the invention, a computer-implemented system similar to the one described above processes secure electronic documents from one or more content providers in accordance with subscriber instructions. Again, the system has a processor and a set of modules such as code that configure the processor or its host machine, including a monitoring module as described above. In accordance with this aspect of the invention, a determination module is operative within the processor to determine any designees of the subscriber and contact information one or more of the subscriber and any designees and a transaction module is operative within the processor to distribute a transaction addressed to at least one of the subscriber and any designees. Each transaction distributed by the transaction module includes one of a transaction ID and a derivative transaction ID derived from the transaction ID.

In still a further aspect of the invention, a computer-implemented system for managing transmission of encrypted electronic documents over a network is described. The electronic Documents include publicly inspectable metadata that is utilized in the exchange between a content provider and a subscriber. The system has a database having a plurality subscriber addresses and up to a plurality of supplemental addresses associated with each subscriber in relation to a document-type of the content provider. A management station has a processor that is configured by code, including optionally a plurality of code modules or a single program. The code executes in the processor to receive a particular electronic document having the metadata, obtain the public metadata associated with the particular electronic document, retrieve from the database routing information for the particular electronic database on the basis of the obtained metadata, and route the particular electronic document in accordance with the retrieved routing information.

In yet another aspect of the invention, a computer-implemented system that can be utilized by a content provider is configured to prepare content having a content type for transmission as an electronic document over a network from the content provider to a managed subscriber having a subscriber ID. The system includes a processor and a set of modules such as code that configure the processor or its host machine. A content enrichment module is operative within the processor to output an enriched content. The enriched content includes the content, public metadata, and private metadata. The public and private metadata in the enriched content is included in accordance with a standard template associated with the content type and maintained by a trusted resource independent of the content provider. A validation engine is operative within the processor to identify the content type and to compare the private metadata to the standard template associated with the content type to produce a validation signal. A key generator module is operative within the processor to respond to requests with a PRN key. An encryption module is operative within the processor, is in communication with the key generator module, and is further operative in accordance with the validation signal to request and receive the PRN key and to encrypt the content and the private metadata using the PRN key. A transaction formatting module is operative within the processor in response to any encryption by the encryption module so as to create a record that comprises the encrypted content, the encrypted private metadata, and the public metadata. A request module is operative within the processor in response to creation of the record so as to request the trusted resource for an asymmetric key and so as to include the asymmetric key in the record, wherein the asymmetric key is a public key asymmetric encryption of the PRN key. A distribution module is operative to distribute the transaction to the trusted resource.

Still a further aspect of the invention concerns a method for managing transmission of encrypted electronic documents over a network between a content provider and a subscriber. The method includes code that executes within processors of machines that are configured by the code to perform the steps of the method. The code executes at respective stations used in the method steps. At a content provider station, an electronic document that is to be sent to a selected subscriber is encrypted using a symmetric key securely retained at the content provider. Also at the content provider station, an asymmetrically-encrypted, symmetric key (AESK) is received, wherein the AESK is provided by a transaction management station in relation to the particular subscriber and the content provider. At the content provider station, a transaction is constructed that includes the encrypted electronic document, the AESK, and publicly inspectable metadata. The transaction is distributed to the transaction management station. At the transaction management station, a routing is determined for the transaction using the publicly inspectable metadata. The transaction is routed to at least one client station based on the determined routing. The transaction is unbundled, at the client station, by applying a private portion of an asymmetric key pair utilized to create the AESK, said private portion being associated with the particular subscriber and the content provider.

These and other aspects, features and arrangements of the invention can be further appreciated from the accompanying description of Certain Embodiments of the Invention and the Drawing Figures.

BRIEF DESCRIPTION OF THE DRAWING FIGURES

FIG. 1 describes an electronic commercial mail distribution network in accordance with the present invention.

FIG. 2 describes a simplified functional block diagram of the electronic commercial mail distribution network identified in FIG. 1.

FIG. 3 describes a simplified block diagram of an electronic commercial mail provider station.

FIG. 4 describes a simplified block diagram of an electronic commercial mail financial intermediary station.

FIG. 5 describes a simplified block diagram of an electronic commercial mail eDoc Reference Data Station.

FIG. 6 describes a simplified block diagram of an electronic commercial mail eDoc Transaction Management Station.

FIG. 7 describes a simplified block diagram of an electronic commercial mail recipient station.

FIG. 8 describes a consumer registration process that establishes the consumer as a unique member of the network and builds initial subscription relationships.

FIG. 9 depicts a recipient subscriber registration screen in accordance with the present invention.

FIG. 10 depicts a provider subscriber registration screen in accordance with the present invention.

FIG. 11 describes the user interface utilized by EM Subscribers to search for eDoc Providers and other EM Subscribers they would like to add to their network for the purpose of creating subscription relationships.

FIGS. 12A and 12B describe the user interface utilized by EM Subscribers to establish and modify copy/forward subscription relationships within the ECMDN.

FIG. 13 is a high level description of the data structure utilized to manage copy/forward functionality within the ECMDN.

FIG. 13A is a high level description of the data structure utilized to manage a multitude of private encryption keys within the EM Subscriber's eDoc Reader.

FIG. 14A is a high level description of a typical public metadata template utilized in the operation of the ECMDN.

FIG. 14B is a high level description of a typical private metadata template utilized in the operation of the ECMDN.

FIG. 15 depicts a typical embodiment of the EM Subscriber's eDoc Reader user interface.

FIG. 16 depicts a simplified flow diagram of the electronic commercial mail document transaction creation and distribution operation of the preset invention.

FIG. 16A depicts an alternative flow as between the content provider and the EM system prior to distribution of an eDoc to a subscriber or any supplemental recipient designated by the subscriber.

FIG. 17 depicts a simplified flow diagram of the electronic commercial mail document delivery exception and subscriber alerting operation of the preset invention.

FIG. 18 depicts a validation engine that can be used in connection with certain embodiments of the invention to confirm compliance by individual content providers with standardized templates used by all participants in the EM system for any given content type.

DETAILED DESCRIPTION OF CERTAIN EMBODIMENTS OF THE INVENTION

By way of overview and introduction, an exemplary embodiment is described which implements several aspects of the invention. The invention is capable of other implementations than as embodied in the particular embodiments illustrated herein. The embodiments described herein, however, provide an expedient for enabling a person of ordinary skill in the art to make and use the invention.

Turning then to FIG. 1, a simplified view of an electronic communications network 100 is illustrated. The network can comprise both public and private segments. For instance, the network segments can include one or more of the following: the Internet, dedicated communications circuits, wide area networks or other types of communications networks. The network 100 is utilized to collect and distribute referential data that is used, in accordance with a salient aspect of the invention, in order to structure and control the flow of content and transactional records that contain the actual content that is to be distributed between the entities and devices in accordance with the broad teachings of the present invention. Associated with the communications network 100 is an Eco Mail (“EM”) system 102 that can include one or more machines that process eDoc transactions in support of eDoc delivery between content providers and subscribers to the Eco Mail system. More particularly, the users include eDoc Providers 110 a-c, Financial Intermediaries 120 a-b, eDoc Reference Data Station 130, eDoc Transaction Management Station 140, Email Providers 150 a-b, and EM Subscribers 160 a-d. These are discussed in turn. Also, the EM system 102 including each of its modules, stations, and machines can further have data storage local to the machines that support its operations or the data can be stored in the cloud that includes the network 100.

eDoc Providers (hereinafter, “Providers”) 110 a-c comprise (1) large commercial institutions who interact directly with the electronic commercial mail distribution network (ECMDN), (2) moderate sized commercial institutions that may act through an intermediary eDoc Aggregator 115, to provide specific services related to formatting content and connecting to the ECMDN, and (3) small commercial entities that outsource content production and management to a third party that creates and maintains source content and provides services to format such content and connect and transmit the formatted content to the EMCDN.

Financial Intermediaries 120 a-b comprise those financial institutions and financial service providers that provide financial management software and/or services to EM Subscribers 160 a-d.

The eDoc Reference Data Station (“RDS”) 130 comprises a centralized hub that can be accessed by all of the participants of the system. As such, the RDS 130 can be and preferably is used for the purposes of: controlling registration as a member of the ECMDN, receiving data that uniquely identifies each participant, searching for other members of the network, and creating subscription relationships between and among members to facilitate, and control, and secure content communication and management and to establish and maintain alerting rules and delivery mechanisms. The code for the RDS 130 and its functionality are described in further detail in relation to FIG. 5.

The eDoc Transaction Management Station (“TMS”) 140 also can comprise a centralized hub having a processor and code executing therein which is operative to format, validate, secure, transmit, and track all transactions within the embodied ECMDN. In one embodiment, code executes locally within a processor of the hub to provide this functionality. The code for the TMS 140 and its functionality are described in further detail in relation to FIG. 6.

The RDS 130 and the TMS 140 each have communication facilities (e.g., a network interface card and respective communications modules) to support communications therebetween and with other nodes on the network 100. Stations 130, 140 communicate with each other, for example, in order to insure that a valid subscription exists for each requested eDoc Transaction, to identify subscriber routing, to identify copy and forward requirements and addresses for each transaction, and to determine the correct public encryption key for each transaction.

Email Providers 150 a-b can be an Email Provider of any scale, but are envisioned as typically being a commercial Email Provider providing generalized email services to a broad audience. It should be understood, however, that Email Providers 150 a-b can be entities that have a dedicated purpose of receiving, managing and forwarding ECMDN transactions.

EM Subscribers 160 a-d are individuals or other entities who have registered with the EMCDN in order to receive and manage commercial content through the system of the present invention.

It should be understood that all communications among the participants that utilize the system can be performed in a conventional manner with existing protocols, such as HTTP or HTTPS or FTP, as a few non-limiting examples.

FIG. 2 is a functional block diagram of the ECMDN depicted in FIG. 1 showing interaction between and among its constituent components. As detailed in FIG. 2, communications take place through an electronic network which may be private or public. Providers 110 a-c communicate directly or, through an eDoc aggregator 115, with the RDS 130 and the eDoc TMS 140.

The Providers identify themselves to the eDoc RDS 130 as members of the ECMDN and submit search requests and retrieve information about customers associated with them who are EM Subscribers 160 a-d of the ECMDN. In addition, the Providers can retrieve templates and information about the data and formatting standards that are required for particular eDoc transactions.

Communications by the Providers 110 a-c with the TMS 140 are made in order to initiate and track eDoc transactions with EM Subscribers 160 a-d who have previously been identified as customers and who have subscribed to receive communications in the form of eDocs from specific Providers 110 a-c.

On the other hand, EM Subscribers 160 a-d can communicate directly with the RDS 130 to provide information about themselves as members of the ECMDN, to search, identify and subscribe to receive eDoc communications from Providers 110 a-c. EM Subscribers can also manage supplemental eDoc delivery of transactions that are addressed to them, including copying other subscribers on certain types of content and forwarding content to a subscriber who has assumed fiduciary responsibility for the forwarding subscriber.

Communications between EM Subscribers and the RDS 130 typically include at least one segment over a public network such as the Internet. Communications between Providers and the RDS 130 can be conducted the same way, or may transpire over a VPN or other private connection.

A Financial Intermediary 120 also can communicate directly with the RDS 130 in order to obtain and reconcile referential electronic payment delivery information that has been provided by the Providers 110 a-c. Email Providers 150 a-b communicate with the TMS 140 to receive, acknowledge, deliver and confirm eDoc transactions that are to be delivered to EM Subscribers 160 a-d that are among the Provider's clients.

With reference now to FIG. 3, the major components of an eDoc Provider station 110 are illustrated. A network interface card 310 connects the station to the network 100 and supports bidirectional communications. A processor 320 and a memory 330 operate in support of a set of modules or code that is configured to provide the requisite functionality described hereinafter. As will be appreciated, the station 110 can comprise a one or more computing machines and can be configured as a network server or servers. It should be appreciated as well that an embodiment of the invention can have certain functions performed by the eDoc Aggregator 115 rather than by the eDoc Provider station 110, and in that case the code or hardware can be included in that machine instead.

The memory 330 stores the source content of a Provider that is to be converted into an eDoc. The memory can have virtual or physical partitions, and source content can be stored, for example, in area 330 a. Metadata concerning the source content can be stored in another partition, such as area 330 b and used by the ECMDN to create a valid eDoc Transaction. The metadata specifications can vary based on many factors such as industry, industry sub-category, and document type. In part, the metadata includes subscriber eDoc Content Metadata such as Provider id, subscriber id, industry, industry sub-category, document type, customer account number, response required indicator, response required date, period start date, period end date, total amount due, and minimum amount due. The metadata can be an extensible format and vary as a function of document type, industry and other factors, as noted.

Each Provider ascertains the requirements for the source content conversion by communicating with the RDS 130 to identify and retrieve the appropriate EM Metadata Template. The template can be stored in another partition of the memory of the station 110, such as area 330 c. EM Metadata Templates are described in more detail in FIG. 14. The memory 330 also stores the EM Recipient's GUID, such as in area 330 d. The EM Recipient GUID is ascertained from valid subscription relationships by communications between the eDoc Provider station 110 and the RDS 130.

The station 110 also can include code that is operative to manipulate the data in memory areas 330 a-d so as to provide standardized formatting and eDoc security features before a transaction is sent to the ECMDN. The code can be stored within the station, such as within portions of the memory 330 (as illustrated), or within a storage device that is in communication with the station and is accessible to the processor 320. There are four core code-portions that are preferably implemented as software. The code can comprise one or more programs or libraries that, when executed, cause the station 110 to have the functionality described immediately above.

One program code portion comprises Symmetric Encryption Software 330 e which encrypts the source content in a manner that can be decrypted with the same key used for encryption. Another code portion comprises EM Pre-Transaction Preparation Software 330 f which can assemble, format and submit to the ECMDN the encrypted Subscriber eDoc Content Data, the symmetric encryption key utilized to encrypt the Subscriber eDoc Content Data, the Subscriber eDoc Content Metadata, and the eDoc Provider's unique internal transaction key. Alternatively, the EM Pre-Transaction Software 330 f can be configured to generate a symmetric encryption key upon successful validation of required formatting and metadata and to request from the TMS 140, an asymmetrically encrypted version of the symmetric encryption key as further described in FIG. 16A.

Additionally, the EM Pre-Transaction Software can communicate with the TMS 140 in order to have the content formatted, validated, secured, transmitted, and tracked by the TMS 140 as it moves through the EM system. Another program code portion comprises Network Software 330 h which handles communication of data to and from the network 100. Another program code portions comprises EM Post Transaction Tracking & Management Software 330 i which validates that all transactions submitted to the ECMDN are properly processed, and which, upon determining that a transaction may not have been received or processed correctly by the ECMDN, re-initializes such transactions. A Transaction Storage area of the memory, such as area 330 g, can be utilized to maintain a log of the transactions submitted to the ECMDN and their current state.

FIG. 4 depicts the components of a Financial Intermediary station 120, illustrated as a single machine though the invention is not so limited. A NIC 410 provides network interface communication to the network 100 in support of bidirectional communication. A local processor 420 and a memory 430 are used to execute program portions, preferably in the form of software, to cause the station 120 to perform the matching functions described below. The memory 430 can have virtual or physical partitions so as to store eDoc Provider Specific Reference Data in a portion 430 a. This data can be derived, initially, from systems external to the ECMDN and can come from internal client-relationship data of the financial intermediary or from data entered by users of the financial intermediaries' existing systems. The reference data is such that it contains sufficient attributes to allow execution of the eDoc Provider Reference Matching Software 430 b to search for and uniquely identify Providers from the RDS 130. Apart from that requirement, the reference data can take on a variety of forms. Execution of the software 430 b in the processor of the station 130, if successful, has a unique match to an eDoc Provider, and the eDoc Provider Specific Reference Data 430 a is thereafter updated by the software 430 b to include the Provider ECMDN's GUID and electronic payment delivery information. Memory 430 also contains Network Software 430 c which handles communication to and from the network 100.

The Reference Data Station 130 is described next with regard to FIG. 5. The RDS 130 includes a NIC 510, processor 520 and memory 550, of the type as previously described. Of pertinence here, the RDS 130 also includes a user interface 525 that includes a presentation through a display device 530 and connectivity to an input device 540. In a preferred embodiment, the display device 530 is a monitor and the input device a keyboard, but the input/output devices can be implemented otherwise so long as they conveys data in a recognizable form to and from a human being. Memory portion 550 a stores EM Registration Software which is operative to allow new subscribers and Providers to register themselves with the ECMDN. This program portion collects meaningful data from the user to tie the user's ECMDN identity to physical locations where he or she receives or creates goods, services and/or paper documentation, and also ensures that registrants provide an email address that is within the domain of an Email Provider 150 a-b that is a participant in the ECMDN so that eDoc transactions can be routed to the EM Subscriber once they are registered.

Turning briefly to FIG. 8, a high level flow of the initial registration process provides a more detailed depiction of the operation of the EM Registration Software. Also, FIGS. 9-10 depict a user interface portion configured to present a form to a user for data capture and submission to the RDS 130. In part, these figures depict an example of data elements that can be required for registration.

Registrants are also required by the EM Registration Software 550 a to validate their identity. In one embodiment of the invention, validation can be accomplished by the registrants accessing the software via a trusted source. The trusted source can be a financial intermediary with whom the registrant has already established their identity. Validation can alternatively be achieved via testing against a third-party database. Thus, for example, validation can comprise correct responses to a series of queries posed through the user interface 525 against a known set of data about a registrant from a third-party database, such as a credit bureau.

Memory portion 550 b contains a multitude of EM Metadata Templates that can be accessed by Providers 110 a-d to insure that the proper metadata and format requirements for each specific type of eDoc transaction are met. Memory portion 550 c can have the EM Provider/Recipient Subscription Software. This software allows EM Subscribers to establish and manage a set of subscriptions with various Providers from whom they are willing to accept eDocs. The subscription software further allows EM Subscribers to more granularly control what types of eDocs they are willing to accept and potentially with what frequency. Subscriptions can be generated by automated look-ups against an existing list of physical mail providers, by direct entry of an eDoc Provider GUID, by manual search or as an affirmative response to a proposed subscription by an eDoc Provider. In part, the software in memory portion 550 c, the EM Provider/Recipient Subscription Software, can include a routine that performs such automated look-ups.

Memory portion 550 d can have the EM Recipient Copy/Forward Rules Software. This software allows subscribers to create and manage relationships with other ECMDN subscribers for the purpose of sharing with or having other subscribers manage some or all of their eDoc transactions.

FIGS. 12A and 12B depicts one embodiment of the user interface of the copy/forward aspect of the EM Recipient Copy/Forward Rules Software 550 d and provides greater detail with regard to what data elements are required to enable the functionality. FIG. 13 describes the data structure required to enable the copy/forward functionality, and also provides greater detail of the copy/forward functionality.

Memory area 550 e contains EM Subscriber Alerting Methods & Rules Software which accepts information from subscribers in connection with how and when they would like to be notified of eDoc transactions that have required actions which need to be performed. This data is utilized by the EM TMS 140 to provide automated notifications and reminders. Such notifications are central to a broad aspect of the invention of managing paperless communications automatically after they have been conveyed to the subscriber. In this regard, a suitably configured interface includes can capture user alert preferences in relation to each Provider. This can be done in conjunction with the subscriber establishing a relationship with the Providers using the EM system 102, or at a later time. The interface captures data associated with the Provider, such as the number and frequency of any alerts, whether follow-up procedures should be used (e.g., automated phone calls and IVR processing), and the timing of the notifications. For instance, if a particular Provider requires payment 30 days from the transmission of an invoice, the subscriber can set an alert for that Provider of increasing urgency, starting, say, ten days before the due date with a change of the message to yellow, and then to red as the due date draws nearer coupled with a phone call to the subscriber to announce the impending deadline, etc. The appropriate action-required dates can be automatically derived from the “Action Required Indicator” and “Action Required Date” fields of the public metadata associated with any eDoc transaction of a content type having such a field, and a subscriber may be able to add preferred reminders and the like or otherwise modify or create an action-indicator. Memory 550 also contains Network Software in area 550 f to handle communication of data to and from the network 100.

FIG. 6 depicts the eDoc TMS 140. The TMS 140 has a NIC 610, a processor 620 and a memory 630 as previously described. A memory portion 630 a stores EM Subscriber Reference Data while memory portion 630 b stores EM Metadata Templates. The templates, as described above, are communicated to the TMS 140 from the RDS 130. The EM Subscriber Reference Data is utilized by the EM Transaction Preparation Software stored in memory portion 630 c to insure that, for each eDoc transaction, a valid subscription agreement exists between the eDoc Provider and the intended recipient. This data is further utilized, when a transaction has been validated, to determine what supplemental copies of the transaction are to be created, which public asymmetric encryption key is to be utilized to encrypt the eDoc transaction, and to assign the correct email address for forwarding each copy of the completed formatted and encrypted eDoc transaction. The EM Metadata Templates are also utilized by the EM Transaction Preparation Software 630 c to validate that the necessary metadata and format requirements for each eDoc transaction have been met.

Memory portion 630 d includes Asymmetric Encryption Software which is utilized to encrypt the symmetric encryption key that is used by the eDoc Provider to encrypt source content. The public half of the asymmetric key is known only to the TMS 140. In particular, the public key portion is not disclosed to others, including members of the ECMDN. This allows EM Subscribers 160 a-d to be sure that each eDoc transaction that is presented to them is authentic and is based on a valid subscription agreement between the Provider and the recipient. Use of the Asymmetric Encryption Key, and the fact that all valid eDoc transactions are routed through the TMS 140, provides a reliable mechanism to filter eDoc transactions from other emails on an automatic (programmatic) basis. In this way, all electronic traffic other than messages subscribed to by an EM Subscriber can be filtered.

Depending on the implementation, the TMS 140 can apply the asymmetric key and then convey the eDoc to an EM Subscriber 160 a-d, or the TMS can respond to requests from eDoc providers with asymmetrically-encrypted symmetric keys, as described further in connection with FIG. 18 below.

Memory portion 630 e includes EM Transaction Routing and Tracking Software which manages the delivery and state tracking of each eDoc transaction. In this regard, the software updates a database with information concerning the movement of each eDocument. For instance, after creation of a particular document, its being sent to an EM Subscriber, its being received by the EM Subscriber station, its being opened by the EM Subscriber, and its being processed in accordance with any associated metadata can all be tracked by the EM Transaction Routing and Tracking Software as a result of messages conveyed between the EM subscriber and the TMS 140. The EM Transaction Routing and Tracking Software can also track payment status provided b Financial Intermediaries 120 for specific eDocuments.

Memory portion 630 f includes an EM Transaction Audit and Delivery Exception Software which monitors the delivery-state tracking of each eDoc transaction and determines when delivery exceptions exist which must be reported to the provider for remediation. The determination of delivery exceptions can be based on combinations of eDoc transaction state, document type, provider, the passage of time or another prescribed criterion or a combination of such criteria. This software communicates those exceptions to the eDoc provider 110 a-c.

An EM Subscriber Alerting Software is in memory portion 630 g which monitors the transaction state of each eDoc transaction based on the public attributes of each eDoc transaction and subscribes rules established by each EM Subscriber 160 a-d. As described further in connection with FIG. 17, the software controls how and when a user is alerted that eDoc transactions exist that has yet to be taken appropriate action. When conditions exist that require alerting, this software program identifies the alternative methods of communication established by the EM Subscriber 160 a-d and obtained from the EM Subscriber Reference Data in memory portion 630 a and creates those communications. In one embodiment of the invention, communications can be in the form of email messages to one or more email addresses, text messages to communication devices and addresses so equipped, or text-to-voice messages to voice communication enabled devices. Memory 630 also contains Network Software in memory portion 630 h to handle communication of data to and from the network 100.

FIG. 7 illustrates certain components of the EM Subscriber station 160 a-d that are relevant to the operation of the ECMDN; Including a NIC 710, a processor 720, a user interface 725, and a memory 750, such as described above. The user interface 725 is further comprised of a display device 730 and an input device 740 such as described above. Memory portion 750 a includes EM Transaction Reader/Manager Software which is utilized to receive, validate, decrypt, display, manage and store eDoc transactions that have been sent to each eDoc Subscriber 160 a-d. Referring briefly to FIG. 15, typical sample user interface of the EM Transaction Reader/Manager Software 750 a illustrates certain data elements that can be presented, processed, managed and tracked. Memory portion 750 b stores the EM Recipient Transaction Database, a repository of decrypted eDoc transactions and the metadata associated with each eDoc transaction. Finally, memory portion 750 c has Network Software to handle communication of data to and from the network 100.

FIG. 8 is a flow diagram illustrating the EM Subscriber registration process according to one embodiment. As indicated in steps 810 and 820, a potential subscriber accesses the EM RDS 130 either directly as indicated in step 810, or through a financial intermediary who is already a member of the ECMDN 820. When directly accessing the station, the user establishes a logon to the RDS 815 and then completes registration data input 835. (A more complete detail of data required for registration is shown in FIGS. 9 and 10.) Entering the registration data accomplishes three principal purposes: it begins the process of validating the registrant as being who they claim to be; it correlates the EM Subscribers physical mail addresses to their ECMDN address; and it creates a repository of data that can later be used to facilitate automated subscription relationship searches and requests.

If the subscriber begins the registration process by logging on to a financial intermediary with whom he or she has already established an identity 825, much of the required registration and subscription data can be passed to the RDS from the financial intermediary without re-entry of that data 830. When appropriate initial registration data has been provided 835, the subscriber must further validate that he or she is the person claimed to be 840. This validation can be partially or completely inherited through a pre-existing financial intermediary relationship, can be derived from a set of challenges and responses to data sourced from a third-party database, or can be established via a manual process based on the review of physical documentation by a party entrusted to do so by the ECMDN. As indicated in decision tree 845, if a subscriber's credentials cannot be validated, the process will end 850 and the registrant will not be allowed to become a member of the ECMDN until some future date when the validation process is successful. If the registrant's identity can be validated, however, then the registrant becomes a member of the ECMDN and becomes an EM Subscriber 160 a-d. Upon validation, the process flow continues with a EM GUID and a Primary PKI Encryption Key Pair being automatically created for the EM Subscriber, as indicated at step 855. The EM GUID uniquely identifies the subscriber to all ECMDN members and the key pair enables the asymmetric encryption functionality, described above, and is the default key used for eDoc transactions with that EM Subscriber. Secondary PKI encryption key pairs are automatically created when any message/document copy and forward functionality is initiated by an EM Subscriber. (FIGS. 12A, 12B, and 13 provide a more detailed depiction of the secondary PKI encryption key creation and management process, discussed below.) The EM Subscriber then selects either an EM Reader Software Provider 860 or identifies the Email Provider 150 a-b to utilize for eDoc distribution. The selection of either the email or reader provider is used to determine or narrow the choice of the other provider. In one embodiment of the invention, the Email Provider has its own reader that is integrated with the Email Provider's other software. In another embodiment of the invention, third-party providers create versions of a reader that integrate with independent Email Providers. Once the required EM Reader Software has been chosen, the user enters his or her existing email address at the corresponding Email Provider 150 a-b or, if no email address yet exists, the EM Subscriber is provided with a mechanism to create a new email address at the Email Provider. Thereafter, an Initial Setup eDoc Transaction 865 is sent to the EM Subscriber at the designated Email Provider. This initial eDoc transaction notifies the Email Provider that they are the distribution mechanism for the EM Subscriber so that the Email Provider can initialize any necessary features for processing eDocs. For instance, the initial eDoc transaction can provide a link and mechanism to facilitate the initialization and personalization of the eDoc reader software to the EM Subscriber's GUID, the private half of their primary PKI encryption pair, and any subscription, alerting, and/or copy/forward rules that may have been established prior to initializing the eDoc reader software. The initial registration process is completed and the EM Subscriber begins the process of customizing the ECMDN to meet his or her specific requirements.

In process 870, the EM Subscriber connects to the RDS to Establish Subscriptions and Manage Settings. In one embodiment of the invention, the customization process is started by the EM Subscriber as a step in the initial registration process. In this embodiment, the user interface runs on a remote computer and is presented to the EM Subscriber station in a web browser environment to permit remote RDS interaction. In another embodiment of the invention, the user interface is generated by the eDoc Reader software on the EM Subscriber Station and only the data is communicated between the EM Subscriber station and the eDoc Reference Data Station. In both embodiments, the functionality is the same as is described herein.

The EM Subscriber begins the process of creating subscription relationships by interacting with the RDS 130 via the network 100. A program such as the EM Registration Software module 550 a can provide functionality suitable for establishing relationships for the subscriber. If the EM Subscriber had originally registered through a financial intermediary, any relationships known to the financial intermediary can be automatically populated as choices for the EM Subscriber to create subscription relationships 875. If the subscriber did not register through a financial intermediary, he or she is given an opportunity to log on to any financial intermediaries with whom they have pre-existing relationships and who are members of the ECMDN for the purpose of importing any direct or third party relationships that may be known to that intermediary. Upon completion of the import from any financial intermediaries, the subscriber is given an opportunity to log onto any commercial databases that may have data about commercial relationships 880. One such example might be a credit bureau. Thereafter, the EM subscriber is given the opportunity to have the system automatically search for registered EM Providers 885 for other potential matches using a search module that operates to discover EM Providers that have registered with the system already.

When all automated potential matches have been identified, the EM Subscriber is provided with a screen to review potential subscriptions, opt-in and establish subscriber based rules 890 about each provider and each document type. Finally, EM Subscribers can manually search for EM Providers or add EM Providers by directly entering the Providers' ECMDN GUID as described in more detail in connection with FIG. 11.

EM Subscribers define alerts at step 892. This process establishes personalized data and rules that are utilized by the EM Subscriber Alerting Software 630 g in the TMS 140 to provide alerts about eDoc transactions outside of the ECMDN distribution channel, as previously described. Alerting is an important component of the invention in that it replaces and improves upon the visual alerting that physical mail is capable of and which has been an important function of the paper based mail process.

EM Subscribers are able to search, identify, create, copy and forward relationships 895 with other EM Subscribers. A more complete detail of the copy and forward interface and functionality is detailed in FIGS. 12A and 12B. Copy functionality allows certain types of eDocs to be automatically distributed to EM Subscribers designated by the primary recipient EM Subscriber. This functionality allows the recipient to automatically share information with other recipients while not sharing the sub-distribution facts with the eDoc Provider. An example of this embodiment of the invention occurs when a document is the financial responsibility of the primary EM Subscriber but is in fact paid or payment is shared by another EM Subscriber (e.g., bookkeeper). Forward functionality is a more structured method of redistribution that is intended to allow a proxy to manage eDocs that have been sent to a specific EM Subscriber. The forward functionality allows the primary recipient to designate another EM Subscriber to receive all of their eDocs and redirects, rather than copies, of the original eDocs. Forwarding is preferably to only one designated EM Subscriber. An example is when the designated EM Subscriber takes fiduciary responsibility the primary EM Subscribers commercial affairs.

FIGS. 9-10 depict simplified versions of the ECMDN registration screens for EM Subscribers (FIG. 9) and Providers (FIG. 10) performed by the EM Registration Software 550 a. These screens are transmitted to a potential new ECMDN registrant via network 100 for presentation in the user interface of any network-connected computing station. An embodiment of this aspect of the invention can comprise a web browser executing on a conventional machine such as a personal computer connected to the Internet.

FIG. 9 depicts the registration data requirements in the context of a data entry form as may be presented to a potential EM Subscriber 160 a-d. Input area 910 includes a number of fields to capture a multitude of name components to both identify the EM subscriber to the network and to facilitate complex and accurate subscription searches. The name input area is further broken down into primary name components 912 and supplemental name components 914. Both component areas of the user interface provide for names to be broken into several discrete data components first name, middle name, last name, salutation prefixes, generational name suffixes and professional designations. The supplemental name components 914 differ from the primary name components in that multiple entries may be included in each field as well as specific negative field identifications. Negative field identifications allow the user to improve search results when the user is aware of other persons with similar names and addresses as might be typical of multigenerational members of a single family. In a typical example, a subscriber might indicate that they are Jr or Dr., but not Sr. or III.

Input area 920 is part of the same data entry form and allows the potential subscriber to enter a multitude of physical addresses where they currently receive mail. As illustrated, a window captures the primary address information and additional windows can be presented for supplemental address information. This data is utilized for subscription matching purposes.

Input area 930 allows the potential subscriber to enter a multitude of email addresses to be utilized. Input area 932 requires that the potential subscriber enter an email address that is to be utilized for eDoc transaction distributions. This email address must be a valid address from an Email Provider 150 a-b who is a member of the ECMDN. Preferably, the registration software automatically validates that an eDoc distribution email address is valid and prevents the user from proceeding if a valid address is not identified. Further, if the potential subscriber does not have an email address that is valid for eDoc transactions, he or she is presented with an option to immediately create an address with any of a multitude of Email Providers 150 a-b who are members of the ECMDN. Input area 934 allows the potential subscriber to enter additional email addresses, though these need not be utilized for eDoc transactions and are not required to be from Email Providers who are members of the ECMDN. The purpose of the alternate email addresses is to facilitate improved subscriber/provider matching and also for EM Subscriber alerting, if this feature is enabled by the EM Subscriber.

Input area 940 captures a multitude of telephone numbers from the potential subscriber. These telephone numbers can be utilized to facilitate improved subscriber/provider matching and also for EM Subscriber alerting, if this feature is enabled by the EM Subscriber.

Finally, input area 950 allows the potential subscriber to enter his or her social security number. This data is also utilized to facilitate improved subscriber/provider matching. As can be appreciated the depth of data provided through the form of FIG. 9 enables the system to perform complex search and match operations and thereby automate the subscription process.

FIG. 10 depicts a form useful for collection of data for a potential eDoc Provider 110 a-c. Input area 1010 allows the potential eDoc provider to enter a multitude of business names to both identify itself to the network and to facilitate complex and accurate subscription searches. The potential eDoc provider enters at least one business name 1012 a and optionally a multitude of alternative business names 1012 b-d that can be used to improve search results. Input area 1020 captures a multitude of physical addresses the eDoc Provider currently receives mail or utilizes otherwise to facilitate the outsourcing of business processes. Input area 1030 provides for the entry of a multitude of attributes about the business and the types of eDocs that the eDoc Provider intends to send. These attributes are utilized to determine which metadata templates 550 b are to be utilized by the eDoc Provider and enables standardization of eDoc transactions and eDoc transaction processing by the EM Subscriber 160. Attributes specified in area 1030 are also utilized by the EM Provider/Recipient Subscription Rules Software 550 c to enable detailed provider/recipient subscription rules. Additionally, input area 1040 provides for the entry of financial account information of the potential eDoc provider. In one embodiment of the invention, this information includes data required to facilitate payment to the provider through the ACH Network and various credit processing networks. Other additional embodiments are possible. The data collected in input area 1040 is utilized to enhance the eDoc Provider Specific Reference Data 430 a in the Financial Intermediary station 120.

FIG. 11 depicts part of a user interface that can be utilized by EM Subscribers to search for Providers and other EM Subscribers that they would like to add to their network for the purpose of creating various types of subscription relationships. In all described embodiments of the invention, EM Subscriber specified data is searched against registration data provided by all ECMDN participants and stored in the RDS 130. Search queries are provided over the network 100 from a machine operated by the client for execution at the RDS 130. By executing searches through the user interface, EM Subscribers can build their network of potential subscription relationships. As previously described in FIG. 8, however, relationships can be automatically searched based on registration information provided by the EM Subscriber and information which has previously been stored in third party databases. Typical examples include electronic banking databases, credit bureau databases, and financial software. Providers can also initiate searches for EM Subscribers that are already their customers by requesting the ECMDN search against a file of customer data provided by the eDoc Provider. The automated processes may not identify all eDoc Provider relationships or may not do so in a timely enough manner to satisfy a particular EM Subscriber. Additionally, when an EM Subscriber desires to establish a subscription relationship with another EM Subscriber for the purpose of copying or forwarding documents, there may be no appropriate automated method to use at all. Accordingly, a mechanism is provided for EM Subscribers to search and add other ECMDN members to their personal network within the ECMDN. Input fields 1110 allow the EM Subscriber to enter various criteria to search the ECMDN participants with matching criteria.

The fields 1110 permit the EM Subscriber to enter one or more of the criteria they know. Some fields, like the Eco-Mail ID 1115, the Telephone Number 1125, and the Email Address 1130, can be very effective at narrowing the results to either a single or a small number of members of the ECMDN. Other fields like Zip Code 1120, City 1130, State 1135 and Street Address 1140 and Name 1145 may require multiple fields be entered to narrow the results to a small enough set.

The lower portion of FIG. 11 depicts a results window having a region 1150 that displays the results of the search criteria and is automatically updated as more search criteria are added. The results can be searched by scrolling through the results list or by sorting on any of the fields of data (columns, as illustrated) displayed. When the EM Subscriber has identified the correct ECMDN member they check the select box 1155 for that entity and use the submit button 1160 to post the selection.

Submitting a selection invokes further processes. If the entity selected by the user is an eDoc Provider, a specialized eDoc transaction is created and sent to the eDoc Provider. This provides EM Subscriber referential data and requests that a subscription relationship be created. If the selected entity is another EM Subscriber, the selected EM Subscriber's GUID is stored in the selecting EM Subscriber's personal network within the ECMDN for use in subsequent copy and forward functions. FIG. 12A describes the user interface utilized to initiate eDoc copy functionality. This functionality facilitates the management of commercial relationships in ways that the EM Subscriber has become accustomed to, but which are unknown to the eDoc Provider. An example of such functionality would occur when an EM Subscriber receives a document because he or she is legally responsible, but when, in fact, a spouse or other designee actually manages the operational aspects of the relationship such as payment or bookkeeping. The user interface can comprise a grid, as illustrated, which allows in area 1210 an unlimited number of Providers who have subscription relationships with the EM Subscriber to be displayed along a vertical axis and in area 1220 an unlimited number of EM Subscribers who have been added to the EM Subscriber's personal network within the ECMDN to be displayed along the horizontal axis. Area 1230 is a dynamically created grid with a selectable area created for each intersection of eDoc Provider and EM Subscriber. The EM Subscriber designates any additional EM Subscribers to be copied on documents from particular Providers by selecting the checkbox at the corresponding intersection. Each time an intersection is selected, the user interface can invoke a command that displays a screen such as illustrated in FIG. 12B.

FIG. 12B is a further screen within the eDoc copy user interface configured to capture further instructions of the EM Subscriber to further limit the type of documents within each EM Subscriber/eDoc Provider relationship that are to be copied. Area 1240 displays an unlimited number of Providers who have subscription relationships with the EM Subscriber to be displayed along a vertical axis. Area 1250 displays along the horizontal axis all document types that can be provided by any of the Providers with whom the EM Subscriber has a subscription relationship. Area 1260 is a dynamically created grid with a selectable area created for each intersection of eDoc Provider and document type. The EM Subscriber designates any additional EM Subscribers to be copied on documents from particular Providers by selecting the corresponding checkbox at the intersection. Several additional features of this user interface are also displayed in FIG. 12B. Area 1265 illustrates an intersection between an eDoc Provider and a document type that is not a valid selection and is automatically restricted from selection. Area 1270 illustrates an intersection between an eDoc Provider and a document type that has previously been restricted and is not subscribed to by the EM Subscriber and is automatically restricted from selection. Clicking the Submit button 1235 invokes a further process which is critical to the automated management of EM Subscriber designated copy recipients, as described next.

FIG. 13 is an exemplary subset of the data table which is created when an EM Subscriber designates that copies of documents are to be automatically sent to additional EM Subscribers. Such designations by an EM Subscriber are by default private and cannot be viewed by the eDoc Provider. The creation of copies to other EM Subscribers creates a matrix of asymmetric encryption keys that correlate to each unique set of eDoc transaction relationships. As previously described in FIG. 8, an initial primary asymmetric encryption key pair is created when a EM Subscriber registers with the ECMDN. Data relating to the key pair is stored in row 1340. The primary key pair is the default key pair utilized for all eDoc Provider subscription relationships and is utilized for all eDoc transactions with a specific eDoc Provider until the EM Subscriber designates one or more additional EM Subscribers to be copied on documents from a given eDoc Provider. More specifically, describing record 1340, the EM Subscriber GUID 1310 is stored in this record. The Key Type 1305 is stored as “primary” and the public half of the asymmetric encryption key is stored in the PKI Public Key field 1320. The Start Date 1325 also can be stored with a value equal to the time when the record was created. Each record in the table that does not have an End Date 1330 assigned can be considered a current record. Only one current primary key record is permitted for an EM Subscriber.

When a copy designation is created, as described in connection with FIG. 12, a secondary asymmetric key pair is created for that relationship between the primary EM Subscriber and the specific eDoc Provider. Exemplary records are stored in table record 1350-1380. In these cases, the Key Type 1305 stored is “secondary” and the eDoc Provider GUID is stored in the Provider ID 1315 field. The primary EM Subscriber's GUID is stored in the Subscriber field 1310. The ECMDN automatically creates a new PKI key pair and the public component is stored in the PKI Public Key Field 1320 and the time of creation is stored in the Start Date 1325 field. The EM Subscriber GUID of EM subscribers who have been designated as copy recipients is stored in Sub-Subscriber fields 1335. If the primary EM Subscriber adds additional EM Subscribers to an existing eDoc Provider copy relationship, only the new EM Subscribers GUID(s) are added to the existing record. If an EM Subscriber removes the copy designation for a previously authorized subscriber, the previously current secondary record is amended by adding an End Date 1330 and a new supplemental record is created and added to the list of all of the remaining additional EM Subscribers and a new Start Date 1325 is created. Should the copy designation be removed for all additional EM Subscribers, an End Date 1330 will be added to the supplemental record, no new supplemental record is created, and the primary key becomes the default for that eDoc Provider relationship.

The subscriber/provider key look-up table of FIG. 13 preferably also includes entries that track document-type (not shown). Document-types, as described herein, are used in the content management and control process. The entries can comprise additional rows with associated keys.

In addition to the described process, when a supplemental record is created or modified specialized eDoc transaction records are sent to all affected EM Subscribers. For instance, if a new copy subscription relationship is created, the new EM recipient must opt-in to the copy subscription request. And, if an existing relationship is being updated with a new PKI key, the update process can be completely automated and executed through message transfer between the affected parties. In all cases, PKI private key storage is transparent to the EM Subscriber.

FIGS. 14A and 14B are high-level descriptions of typical metadata templates that can be utilized in the operation of the ECMDN. FIG. 14A describes public metadata fields that are common to all eDoc transactions. FIG. 14B describes private metadata fields which may vary based on underlying characteristics of each eDoc transaction. With respect to both public and private metadata, the included data fields represent a subset of metadata that can be included in eDoc transactions, though fewer or additional fields can be included in embodiments of the invention.

Turning to FIG. 14A, the table illustrates along several rows a number of public metadata fields 1410. Public metadata fields are more standardized across eDoc transaction types and are accessible in unencrypted form at various stages of the eDoc transaction process after they leave the Provider's internal systems and before the eDoc transaction is decrypted by the EM Subscriber's eDoc receipt and management software. The public metadata fields are required to be unencrypted so that addressing, asymmetric encryption, routing, auditing and alerting can be performed.

FIG. 14B illustrates a set of private metadata templates that are suitable for a particular industry. As illustrated, the industry is the financial sector, and the sub-industry is banking. The columns identify a selection of various metadata templates 1430 that can be categorized by industry 1440, sub-industry 1445 and document type 1450. The metadata templates 1430 are exemplary and in practice are far more extensive. For instance, the financial industry includes other sub-industries such as brokerage, and other industries include insurance, energy, telecommunications, and so on. Private Metadata fields 1420 are added to the eDoc content prior to symmetric encryption by the eDoc Provider and are maintained securely at all times in the eDoc transaction for use is by the EM Subscriber's eDoc receipt and management software. The primary purposes of the Private Metadata fields is to allow the EM Subscriber software to know the key attributes of any received documents without having to specifically open and examine the full content provided by the eDoc Provider and to facilitate automated organization and management of eDocs.

The standard template maintained for each document type of a given industry/sub-industry has an associated set of private metadata that is particular to that document type. For example, in the insurance industry, health sub-industry, the spectrum of standard templates can include a statement, an invoice, a policy, other legal documents, an service change document, security information, marketing materials, and any other category. By standardizing the template, the EM system 102 can validate—prior to distribution—each transaction that an individual content provider seeks to distribute. Validation is discussed below in connection with FIG. 18. Briefly, a validation engine executing at the eDoc provider station 110 compares the data in the public and private metadata fields of the template to expected values and formats and then supplies a validation signal suitable for action by other modules that govern the construction of the message to be sent to the subscriber (“transaction”). Whether a transaction is sent to the TMS 140 can therefore be made to depend upon a validation of the metadata at the eDoc provider 110, under the content provider's custody and control. On the other hand, transactions that pass this first-stage validation are transferred via the TMS 140 to one or more destinations maintained for the subscriber by the TMS, and the metadata can be used among other things to provide intelligent alert and reporting functionality as described herein.

FIG. 15 depicts an example of the EM Subscriber's eDoc Reader user interface. The depicted interface is one of many ways that the functionality of the eDoc Reader can be expressed. The interface permits action by the EM Subscriber to cause further processing of EDoc transactions such as accepting or denying subscription requests, payment of invoices, invocation of user-established rules, printing, document management, etc. The interface 725 provides an organization for the transactions received from the TMS 140 that extends beyond conventional email programs by providing alerts and action-management rules to better ensure that transactions are noticed, acted upon, and preserved. In part, the interface 725 enables multiple views of received transactions. As illustrated, the “inbox” transactions of all eDoc providers have been selected in the source control panel 1502 a, such as by click-selecting a list of potential sources of received eDoc transactions. The source control panel enables the subscriber to view a dynamically created set of eDoc transactions which may be arranged by action state or by other criteria a subscriber can set by selecting Search Results 1502 b and entering data on a suitable supplemental input screen (not illustrated). The subscriber can also filter the source results by selecting all providers, an individual provider, or a user-selected multitude of providers to which the subscriber is subscribed in the provider panel 1502. This selection presents the un-archived and not-deleted transactions of all providers in the transaction display 1504. If a particular provider is selected, then the transaction display 1504 presents a filtered list of transactions for only the selected provider. The list in provider panel 1502 is dynamically populated in response to subscription-creation pursuant to the process flow of FIG. 8. The interface can include a form 1506 for submitting the identity of an eDoc provider. For instance, the GUID of the provider can be input into the form 1506 to cause a further interface window to be presented, such as illustrated in FIG. 11, in order to enable the subscriber to add or search for eDoc Providers to add to their network of subscription relationships.

The transaction display can alternatively or additionally be configured by interaction with the user to display transactions on the basis of recipients, tags, or date range by selecting a suitable control 1508, 1510, 1512 to call up a respective panel.

The interface 725 is presented by eDoc Reader software 750 a executing on the subscriber's machine 160. The software 750 a can be constructed from a plurality of modules each having functionality to implement the interactive features of the interface 725 (e.g., a search module, an instant subscribe module, panel creation modules, etc.). Transactions, once received, are unbundled by the eDoc Reader software 750 a using the private portion of the asymmetric key pair associated with each subscriber/provider pair. In this regard, it is important to appreciate that while the transactions are delivered to the subscriber from the provider by passing through the TMS 140, the transactions are preferably doubly-encrypted initially with a symmetric key that encrypts the content and private metadata (which encryption is performed by the content provider) and subsequently by an asymmetric key (determined by the TMS 140) that is used to encrypt the symmetric key. This arrangement ensures the confidentiality of the documents being conveyed as the payload of each transaction, while allowing the TMS 140 to use the public metadata for routing, archiving and message tracking purposes.

The eDoc Reader software 750 a is configured, in part, to unpack the document payload and access the private metadata by utilizing the public metadata associated with each eDoc transaction to determine and access the private portion of the appropriate provider/subscriber asymmetric key pair that, preferably, is locally maintained. As shown in FIG. 13A, subscribers have a key table that is similar to the key table at the TMS 140 (see FIG. 13), except the table maintained at the subscriber machine 160 includes the private portion 1350 instead of the public portion 1320 of the PKI key (“PKI Private Key”). FIG. 16 details the unpacking process when a transaction is received at the eDoc Reader 750 a; suffice to say that the PKI Private Key for that subscriber can be applied to the transaction so as to expose the symmetric key used by the eDoc provider 110, and then the symmetric key can be directly utilized to decrypt the private metadata and the content. Once unpacked, the transaction payload comprises a document, such as a pdf or xml file that can be viewed by the subscriber within a window of the reader, or using another program such as Adobe's Reader or a web browser application such as Microsoft's Internet Explorer. The document can be click-selected and opened through the interface 725, such as by clicking on icon 1520. In addition, the public and private metadata of the unpacked transaction is used to populate a database of eDoc transactions and attributes which is further utilized to populate the various columns of the interface, and to provide interactive controls, as appropriate.

One example of an interactive control concerns a transaction of type subscription request. This type of transaction requires user-action and the interface 725 preferably provides controls 1530 to accept or deny the subscription request. Only after accepting the request is there any possibility that a particular eDoc Provider can send transactions to the subscriber or that another subscriber can copy or forward eDoc transactions to the user. This opt-in process precludes “junk mail” from entities with whom the subscriber does not have a subscription in place from cluttering the eDoc Reader. Upon accepting the request, the table in FIGS. 13 and 13A are both updated. The table of FIG. 13A can updated through local processing at the subscriber's machine 160, but updating the table of FIG. 13 is attendant with a message between the subscriber machine 160 and the TMS 140.

The standardization of the templates enables a further important use of the private metadata in an implementation of the invention. More specifically, for transactions that require payment of specified amounts by certain dates, the standard template has those key parameters external of the document itself and within the metadata for use by the eDoc Reader in presenting the transactions with that data arranged to permit sorting by amount due, due date, provider name, and so on. In addition, an interactive payment control 1540 can respond to user action by initiating a payment process on behalf of the subscriber with his or her designated banking institution (e.g., by opening a port and connection to a particular institution from the subscriber machine 160 over the network 100 to that institution). Moreover, a preference file can store the subscriber's preferences with respect to which account to draw against for payment of invoices based on, for example, the vendor identity, the amount due, or the recipient. Likewise, the preference file can initiate an automated transfer, say, from an interest bearing savings account to a checking account as a preliminary step to each invoice payment. The preference file (not shown) can include other settings such as a rule 1550 to pay without waiting for manual action if the amount (say, from a given vendor) is below a prescribed amount. Other rules can govern when-to-archive 1560 a transaction so as to empty the inbox and focus the subscriber on open items.

With continued reference to FIG. 15, the interface can provide a variety of alerts, again using the decrypted private metadata and, optionally, the user preference file, to visually distinguish paid invoices from unpaid invoices, invoices with a due date that is approaching and invoices that have an imminent due date. Such visual distinctions can comprise a color coding such as green, yellow and red to signify increasing urgency as a due date for payment approaches.

The interface also includes conventional navigation features such as searching, file management, editing and the like which can be conventional in design and implementation.

FIG. 16 is a high level depiction of the flow of an eDoc transaction from inception by an eDoc Provider 110 a-c to encryption and routing by the EM TMS 140 through high level eDoc transaction distribution and tracking by an Email Provider 150 a-b and on to final distribution and decryption by EM Subscribers 160 a-d.

Each eDoc transaction begins when an eDoc Provider 110 a-c has some content that is to be communicated to another entity. In the current example, the content is data that has historically been in written form and has been distributed by physical mail delivery, but it should be noted that the content could be video, audio or any other data than can be stored completely in electronic form. The content that is to be sent is initially stored in the eDoc Provider's Content Repository 1602.

The eDoc Provider 110 a-c determines that a recipient is an EM Subscriber by looking at EM Recipient IDs stored in memory 330 d and retrieving content 1604 that is to be turned into an eDoc transaction from the eDoc Provider Content Repository 1602. The eDoc Provider subsequently performs Content Enrichment 1606 by adding any eDoc Content Metadata stored in memory 330 b that is determined to be required by the EM Metadata Template stored in memory 330 c. When the content enrichment 1606 has been completed, Symmetric Encryption of the Enriched Subscriber Specific Content 1608 is performed. Those familiar with the art will recognize that symmetric encryption is a broad term for a widely known set of encryption technologies whose common characteristic is that encryption and decryption can be performed utilizing the same key. In one embodiment of the invention, the key itself is chosen randomly by the eDoc Provider 110 a-c for each eDoc transaction. After the encryption of the data has been completed the eDoc Provider causes an eDoc Pre-Transaction Record 1610 to be formatted. This record includes the encrypted content, the encryption key utilized to encrypt the content, and public metadata (as identified in the EM Metadata Template) stored in memory 330 c. The formatted pre-transaction record is transmitted to the EM TMS 140 in connection with a request for an asymmetric key to use in distributing the transaction, as indicated at block 1612, and is stored in the eDoc Provider Local EM Transaction Database 1614.

Upon receipt by the EM TMS 140, each pre-transaction is checked for validity 1616. Such validity checks can include whether a valid subscription agreement existed between the eDoc Provider and the EM Subscriber for the declared type of document, if the pre-transaction record were properly formatted based on the Provider and document categorization, and if all of the necessary public metadata fields were present and valid. If the pre-transaction record fails validation, the station notifies the eDoc Provider of the transaction exception 1618 along with a detailed error code as to the nature of the exception. The notification can be stored in the eDoc Provider Local EM Transaction Database 1614 for reprocessing. If the pre-transaction passes validation, the TMS 140 communicates with the EM RDS 130 or a subscriber database at the TMS 140 to Determine Asymmetric Encryption Key and Supplemental EM Subscriber Records 1620. This determination can be based on the provider GUID, the subscriber GUID, and the document type of the current eDoc Transaction, using information such as detailed in FIG. 13. Upon completion of the process, as indicated at block 1622, asymmetric encryption of the symmetric key utilized by the eDoc Provider is performed and provided in the pre-transaction record. At block 1624, the formatting and building of the primary and supplemental eDoc transaction records are performed. A further process stores and transmits the eDoc transactions 1626. This process can store the transactions to the EM Transaction State Database 1628, transmit the EM Transaction Number for the Primary eDoc Transaction to the eDoc Provider 1630, and also Transmit all Primary and Supplemental eDoc Transactions to the Designated Email Providers, as indicated at block 1632. The recipients can be ascertained by communicating with the EM RDS 130 to determine the current valid email address for each EM Subscriber 160 a-d.

Subsequently, each eDoc Transaction is received by the designated Email Provider 150 a-b and is checked for validity 1634. The primary validity checks by the Email Provider are to determine if the entire eDoc transaction has been received without data flaw and to insure that the destination email address is correct and deliverable. If the eDoc transaction record fails the validation checks, the Email Provider notifies the TMS at block 1636 such as with a detailed error code as to the nature of the exception. The notification can be stored in the EM Transaction State Database 1628 for reprocessing. If the eDoc transaction passes validation, the Email Provider stores the eDoc transaction and sends an acknowledgment to the EM TMS 1638. The eDoc transaction is stored in the Email Provider's Email Transaction Database 1640 and the EM TMS 140 updates the EM Transaction State Database 1628 to reflect the current state of the eDoc transaction.

Continued routing of the eDoc transaction occurs when an EM Subscriber 160 a-d performs a Sign-in and Email Retrieval 1642 and the subscriber's Email Provider 150 a-b forwards eDoc transaction emails to the subscriber 1644. The Sign-in and Email Retrieval process 1642 can be accomplished by a dedicated eDoc reader which is able to automatically retrieve only eDoc transactions from the Email Provider 150 a-b. Alternatively, the eDoc reader can be incorporated into an existing email reader system, or the eDoc reader functionality can be incorporated into other software that embeds an eDoc reader. More generally, all eDoc readers have a commonality of communication, decryption and content organization which is identified in this FIG. 16 and which is further detailed in FIG. 15. Upon receipt of the eDoc transaction, a reader program operating for the EM Subscriber 160 a-d provides an acknowledgement to the Email Provider 150 a-b. The Email Provider stores this acknowledgement to the email transaction database and also creates and transmits an acknowledgment 1646 to the EM TMS 140 that each specific eDoc transaction has been received by an EM Subscriber. The TMS 140 updates the EM Transaction State Database 1628 to reflect the current state of the eDoc transaction.

The EM Subscriber's eDoc reader automatically decrypts all eDoc transactions and stores the decrypted content and associated metadata to a database associated with the eDoc reader 1648. It should be noted that the eDoc Reader Database 1648 may be located locally to the eDoc Reader software or may be remotely stored and accesses via network 100. The subscriber station also creates and transmits an acknowledgment 1650 to the EM TMS 140 that each specific eDoc transaction has been decrypted by the EM Subscriber's eDoc reader. The EM TMS 140 updates the EM Transaction State Database 1628 to reflect the current state of the eDoc transaction.

Referring now to the process flow of FIG. 16A, a modified flow as compared to the process just described illustrates another path for the creation and movement of content from a eDoc Provider 110 a-c toward a subscriber. In FIG. 16A, like reference numbers are accorded to steps in the flow that correspond to the steps of FIG. 16. In this process flow, the eDoc Provider 110 a-c maintains custody of the content through the encryption and double encryption steps, and only then routes a transaction to the TMS 140 for distribution to Subscribers 160 a-d.

The process flow of FIG. 16A proceeds as described above to retrieve content that is to be sent to a particular Subscriber and then enrich the content with public and private metadata 1602-1606. At step 1607, as a departure from the approach of FIG. 16, the eDoc Provider 110 communicates with the template compliance validation module (TCVM) to validate that the public and private metadata correctly utilize an appropriate EM template that has previously been provided by the RDS 130 for use in various transactions. The TCVM processing is described in greater detail with regard to FIG. 18. Briefly, it comprises a module that resides at the eDoc Provider computer 110 and operates as a “black box,” processing inputs and selectively permitting transactions to advance beyond a proposed stage, as described next.

If the validation is not satisfied, as tested at block 1607 a, the proposed transaction is rejected and the proposed transaction is returned to the eDoc Provider's system for reprocessing 1607 b. Conversely, if the validation is satisfied, the TCVM generates and communicates to the eDoc Provider a pseudo random number, described in more detail below, to be utilized as a symmetric encryption key for the proposed transaction. Thereafter, the eDoc Provider symmetrically encrypts the content and the private metadata with the generated key 1608, and formats the eDoc record including the encrypted content and private metadata on the one hand and the unencrypted public metadata on the other hand 1610. Importantly, the public metadata includes the document type and recipient subscriber. At block 1612, the eDoc Provider communicates with the TMS 140 in order to request that the symmetric key—which already has been utilized to encrypt the content and the private metadata—be asymmetrically encrypted with a key associated with the Subscriber, without transmitting the symmetric key, the content or the private metadata itself.

Meanwhile, the TMS maintains a table of Subscriber keys and is able to validate, at step 1616A, whether the request is to be accepted and return with an asymmetrically encrypted key or not. In part, the TMS has a processor that is configured to use a key-request validation module (KRVM) to examine the request message from the eDoc Provider 110 and act on the request. For instance, the KRVM can comprise code that executes within the processor so as to configure it as such. The request message can include a Provider GUID of the particular eDoc Provider 110 making the request. As a control mechanism, the KRVM can be configured to look up the address associated with the Provider GUD in the message and respond to the address that the KRVM maintains rather than any address in the request message so as to provide a control against spoofing and the like. The request can further include a Subscriber GUID of the Subscriber to whom the transaction is to be delivered and a document type based on the previously validated EM template. The request can, but need not, include a transaction number. The transaction number serves the purpose of uniquely identifying the transaction within the EM system 102, including to uniquely identify the transaction to the TMS 140. The transaction number, for instance, can be a sequentially generated number, and in the form can include two components: a first component that can be the same as the Provider GUID but which is uniquely associated with a particular eDoc Provider; and a second component that is sequentially updated with each request message. Alternatively, the transaction number can be generated independently at the eDoc provider and at the TMS on the basis of receipt of a key request including the Provider GUID which can be used by the TMS to increment the transaction number. The transaction number is further utilized as a seed value that is fed by the KRVM into a pseudorandom number generator algorithm associated with that provider in order to generate a symmetric key. Because that eDoc Provider and the TMS both can determine/share a transaction number and use that number to seed a PRN generator that is configured alike at both stations, a symmetric key can be generated at each station in synchronization with each other. What is important to appreciate then about the flow of FIG. 16A is that the symmetric key is not transmitted from the eDoc Provider 110 to the TMS in the clear.

Thus, at step 1616A a key request can be received that includes a Provider GUID, a Subscriber GUID, a document type and optionally a transaction number. The KRVM queries a secure database to determine if there is a subscriber relationship in place as between that provider and the identified subscriber for the given document type. For example, the database can comprise the table of FIG. 13 and the query can check if the subscriber 1320 identified in the key request has a relationship with the provider 1315 in the key request. If such a relationship does not exist, then the process flow branches to step 1618, as previously described, to provide a notification of the non-validation. On the other hand, if the KRVM module confirms the relationship, then the process flow continues at step 1620A to determine the value of an asymmetric key that can be utilized to encrypt the symmetric key 1622 that was previously identified and utilized by the Provider to encrypt the content and private metadata. The asymmetrically-encrypted, symmetric key (“AESK”) is subsequently returned to the provider in step 1623 to record into a transaction that is ready for distribution across the EM system 102. In particular, the TMS includes a table of keys, as described previously in connection with FIG. 13, and an asymmetric key 1320 can be extracted from the entry in the table that correlates the requesting provider 1315 with the identified subscriber 1310.

Thereafter, the TMS can asymmetrically encrypt the symmetric key that has been independently generated at the TMS and that is the same as the symmetric key that the eDoc Provider uses to encrypt the enriched content for the transaction. At step 1623, the AESK is returned to the eDoc Provider 110. In summary, therefore, the key request 1612A transmits a Provider GUID, a Subscriber GUID, and a document type to the trusted resource that is the TMS 140, and optionally further transmits a transaction number associated with that eDoc Provider. This transmission is sufficient to permit several secure actions at the TMS including: independent generation of a symmetric key; extraction of an asymmetric key associated with that subscriber; and encryption of the symmetric key with the asymmetric key. The eDoc Provider receives the AESK but has no access to any further information about message propagation. The TMS forwards the AESK but has no access to the underlying content; rather, the TMS is the master of keys and relationships while the subscribers to the EM system 102 each have controlled access to the content and managed alerts concerning each transaction. Meanwhile, back at the eDoc Provider, the processor at that station is configured, e.g., by code executing therein, to await the AESK. Once that key is received after step 1623, the eDoc Provider can augment the record and complete the construction of a transaction by adding the AESK to the record. As such, the record includes the encrypted, enriched content and public metadata and now includes the AESK. The transaction includes public metadata in the clear, including a transaction number, that is used by at least the TMS and the eDoc Reader software to distribute the transaction and provide alerts and notifications as described previously. The transaction itself is distributed from the eDoc Provider to the TMS as indicated at step 1613, and the TMS, upon receipt of the transaction, uses the public metadata (in particular, the Provider GUID, the Subscriber GUID, and the document type) to determine the subscriber's address for electronic distribution of this transaction. Upon distribution, the subscriber can view the content, but equally important, the TMS can supplement the distribution with further addresses based on any copy or forward rules that the subscriber can and may have established with the EM system 102 in accordance with a salient aspect of the invention. Thereafter, the process flow is as previously described and includes transmission of a message to the eDoc Provider to confirm delivery of the transaction (step 1630), transmission of the transaction to the identified subscriber and/or any designated recipient(s) (step 1632), and update of a state database (step 1628).

FIG. 17 depicts a flow diagram of the electronic commercial mail document delivery exception and subscriber alerting operation that can be included in embodiments of the preset invention. Providers of mail, whether in physical format or in the form of eDoc transactions can benefit from knowing whether a piece of content has been delivered to the recipient and if it has been “opened.” Recipients of mail also can benefit from being alerted to mail that they have forgotten requires action or that needs immediate attention. The present invention incorporates both of these functions by utilizing the standardized public metadata described in FIG. 14. A process at the TMS 140 reviews the EM Transaction State Database 1628 to identify eDoc transactions that have a last activity timestamp that is more than, for example, 24 hours old 1700. Transactions that have not had activity with the past 24 hours are checked for transaction state exceptions 1705 by measuring time intervals against several elements of previously identified metadata about each eDoc transaction on the EM Transaction State Database 1628. A multitude of exception cases may be identified for each transaction, Provider, recipient, and/or document type. Several exception cases are described here but many more can be implemented within the scope of the invention. In addition to identifying delivery exceptions and providing subscriber alerting, the current process also performs a maintenance function to keep the EM Transaction State Database at an efficient size. The exception state checking process identifies transactions that have a state of “delivered and decrypted” by the subscriber as exceptions. This state indicates that a transaction has been received and seen by the subscriber. Process 1710 specifically checks for this state and if it is found to be valid, moves the eDoc transaction from the EM Transaction State Database 1628 to the Completed Transaction Historical Database 1715. If this is not the cause of the exception the eDoc transaction is further reviewed in process 1720 to determine if the exception state requires notification to the eDoc Provider. In one embodiment of the invention, the process determines the elapsed time between the initial eDoc transaction transmission time stamp and the current time. If the time has been longer than a predetermined time and the status of the eDoc transaction is not, at a minimum, delivered to subscriber, then information about the eDoc transaction is passed to a further process that notifies the eDoc Provider of a transaction exception (including a detailed error code as to the nature of the exception), at block 1725. Once the transaction exception has been sent to the eDoc Provider 1725, the EM Transaction State Database 1628 is updated to reflect the further communication and the time at which the action was taken. This updates the activity timestamp utilized to initiate the exception review process.

The eDoc transaction is further reviewed to determine if any of the exception states requires subscriber notification (alerting) 1730. In an example of this embodiment of the invention, the process determines how much time remains between the current time and the action-required date. Based on criteria that might be selected by the system or by the EM Subscriber for a specific type of transaction, the process determines if subscriber alerting is required. If alerting is required, the process looks up the alerting methods and contact details for each specific transaction 1735. The alerting methods and details can be identified through communication with the EM RDS 130. Once the methods and details have been determined, the actual alerts are sent to subscribers 1745 and the EM Transaction State Database 1628 is updated to reflect the further communication and the time at which the action was taken. This updates the activity timestamp utilized to initiate the exception review process. Referring briefly to FIG. 18, the eDoc Provider station 110 preferably has its processor configured to include a template compliance validation module (TCVM) 1800, such as in the form of code executing in the processor. The TCVM 1800 can be a secure module provided by the TMS and arranged to operate as a “black box” so that its inputs and outputs are defined by the TMS and its operation is secure. The reason for this is that the TMS occupies a position of trust in the EM system 102 and the TCVM enables validation at each content provider of their correct use of a standard template provided by the TMS for use in various transactions. In this way, the EM system can extend the standard templates and have control over compliance at each content provider and individual content providers have an impediment to using the EM system to distribute content that is not in conformance with an accepted content-type for the industry/sub-industry of any particular eDoc Provider.

At step 1802, the TCVM is invoked at the eDoc Provider station, such as in response to the provider having content that is ready to be distributed to a particular subscriber. The module obtains the content (eDocument), private metadata associated with the content/subscriber by the eDoc Provider, and public metadata of the same type. At block 1804, the module identifies the content-type, which is one of the fields common to the public metadata of each of the standard templates used in the EM system 102. At block 1806, metadata is extracted such as fields among the private and public metadata. For instance, the TCVM 1800 can pop a field from the private metadata into a register that is accessible to the processor of the eDoc Provider station. At block 1808, the extracted data is compared to the standard fields of the template for the identified content type. Thus, for instance, each or selected fields of a standard template for a given content-type can be compared to the extracted data to determine whether those values conform to variable definitions for the standard template. Typical variable definitions include, currency, date, time, integer, real, alphanumeric, and so on. At block 1810, a determination is made as to whether the validation is satisfied. If the test is not satisfied, the proposed transaction cannot advance further in the EM system 102. On the other hand, if the content provider has constructed a record in conformance with the standard template (such that all subscribers receive content and controls that are consistent for a given content type, as only the independent, trusted, EM system is able to enforce), then the eDoc Provider station can obtain a PRN key at step 1812, substantially as described above. Briefly, a transaction number can be used to seed a PRN generator module and output a symmetric key. The content and the private metadata for the transaction is encrypted at step 1814 using the symmetric key. Next, step 1612A is performed as described above (see FIG. 16A), and the TCVM module at the eDoc Provider station then awaits receipt to the AESK, as indicated at step 1816. Finally, as described above, the eDoc Provider station can complete the record and distribute a fully constructed transaction to the TMS, as indicated at step 1613.

As will be appreciated, the process flow can be implemented by code executing in a processor and configured to provide the functions described above, and can be implemented in response to subscriber-interaction with one of the interfaces described above and, as such, a practical implementation of the invention does not necessarily perform each of the steps illustrated in the flow diagrams nor does it necessarily execute in the order illustrated. Rather, the flow diagrams are provided for purposes of discussion and not limitation of the invention

In conclusion, embodiments of the invention can create a private network of providers and recipients that establishes each registrant as being the entity they claim to be and provides a guaranteed, unique identifier (GUID). The GUID for a recipient may be associated with multiple physical locations and can be associated with any email address the recipient chooses. The private network utilizes existing email infrastructure and protocols for distribution but implements its own security and content protocols to secure content, implement delivery tracking and automate document management. The GUID for a provider may be based on a single legal entity or subdivisions within an entity. The implementation of GUIDs allows providers to know that they are sending documents to the intended recipient without the requirement to validate each email address. For recipients, GUIDs allow for aggregation across multiple providers and redirection of delivery location with a single entry.

Embodiments of the invention can standardize attributes about each document being conveyed in the system so that many parts of the mundane processes associated with existing document distribution systems can be automated. For example, attribute management using components described herein enable control over the presentation of documents, action-reminders, and archiving by date, provider, type, or role (e.g., the user is a forwarded recipient).

Embodiments of the invention can enable the recipient to control which providers can send documents to their GUID and what types of documents each provider can send to the recipient. This functionality will be controlled through the use of a subscription process and stored profile information. When initiated by recipients, the subscription process can be immediate. When initiated by providers, the subscription process requires recipient acceptance or “opt-in.” The subscription process can be automated utilizing pre-existing sources of data, can be driven by search criteria or can be facilitated by direct entry of a GUID. No document will be distributed without a valid subscription. Unique identifiers as well as routing limitations enable the recipient's Email Provider to easily separate email traffic from the document distribution network.

Embodiments of the invention can provide a higher degree of security to the recipient than is current practice for both physical mail and traditional email. This functionality can be accomplished through the use of an automated, double encryption code. As described herein, a symmetric key can be used to encrypt messages, with the system 102 including a machine that receives the symmetric key and encrypts that key with an asymmetric key. The message (e.g., email) is ultimately conveyed to the viewer in an encrypted format. The message is encrypted with the symmetric key and so are the standardized attributes concerning the content of that message, but the symmetric key is not communicated as such. Rather, the symmetric key is communicated in a further encrypted form, namely, after encryption by a second, asymmetric key. In one embodiment, the encrypted document, the encrypted symmetric key and accompanying content-attributes (necessary to manage the distribution) are communicated by a machine associated with the system 102 rather than the content provider itself (e.g., a transaction management station) which utilizes the public key of the recipient's GUID to encrypt that content provider's encryption key. Utilizing this methodology, all document messages stored anywhere on the Internet can be encrypted and document distribution can be limited to the recipient because the “public” key will not be widely distributed.

Embodiments of the invention also can enable providers to determine if a document has been delivered with a high degree of accuracy. To facilitate this functionality, the document distribution network adds a unique document identifier to each distributed document and tracks the delivery status of each document. The first state of document delivery is an acknowledgement that the transaction has reached the recipient's mail server; the second state is an acknowledgement that the recipient's mail client has received the transaction. The final delivery state is recorded when the recipient has decrypted the document. The decryption and response are automated by the recipient's application and, if the recipient is offline at the time of decryption, the result is stored until the user next retrieves email of any type. Exceptions to delivery can be reported to the provider for follow-up action, and details of all delivery data can be available to the provider for auditing and other purposes.

Embodiments of the invention can ensure that users do not forget to retrieve or take required action on documents on a timely basis. The delivery state mechanism described above can also be used to trigger alarms to the recipient. Such alarms can be triggered by time and state rules for each document provider, each document type or both, and be delivered through a combination of email to alternative addresses, text messages or even text-to-voice messaging to traditional voice communication devices.

Embodiments of the invention can to allow recipients to set up automated forwarding and copying of documents to other, generally related, recipients. A typical instance of the requirement for this feature is a document addressed to an older parent or disabled sibling who has his or her messages managed by a different recipient. To facilitate this functionality, a recipient creates, on the document distribution network, a “copy” or “forward” functionality to another recipient. This functionality can be on a complete or partial basis (specified by provider or document type, for example). Another example is when an invoice is addressed to a husband or wife but is generally paid by the other spouse.

Embodiments of the invention also can allow financial intermediaries to search, identify, access and store the GUID and profile data of each registered provider. Provider profile data includes mailing address as well as account data to facilitate electronic payments. This functionality allows financial intermediaries to access data required to deliver payments to provider members of the network as instructed by subscribers who are customers of each financial intermediary. The utilization of standardized GUIDs in transactions initiated by providers insures that payments will be sent to the correct provider in the most expeditious manner possible. In this regard, the system 102 can allow financial intermediaries to send specialized messages so as to update transaction statuses and provide Providers and Subscribers with more comprehensive message management. For example, the financial intermediary can provide notification of completed payments to improve auditing and more detailed alerts for the benefit of the subscriber.

While the invention has been described in connection with certain embodiments, it is defined by the claims that accompany this description and is not to be read as being restricted to any one embodiment thereof. 

I claim:
 1. A computer-implemented system for preparing content having a content type for transmission as an electronic document over a network from a content provider to a managed subscriber having a subscriber ID, comprising: a processor; a content enrichment module operative within the processor to output an enriched content that includes the content, public metadata, and private metadata, wherein the public and private metadata in the enriched content is included in accordance with a standard template associated with the content type and maintained by a trusted resource independent of the content provider; a validation engine operative within the processor to identify the content type and to compare the private metadata to the standard template associated with the content type to produce a validation signal; a key generator module operative within the processor to respond to requests with a pseudorandom number (PRN) key; an encryption module operative within the processor, in communication with the key generator module, and further operative in accordance with the validation signal to request and receive the PRN key and to encrypt the content and the private metadata using the PRN key; a transaction formatting module operative within the processor in response to any encryption by the encryption module so as to create a record that comprises the encrypted content, the encrypted private metadata, and the public metadata; a request module operative within the processor in response to creation of the record so as to request the trusted resource for an asymmetric key without transmitting the PRN key in the clear to the trusted resource and to include the asymmetric key in the record, wherein the asymmetric key is a public key asymmetric encryption of the PRN key; and a distribution module that distributes the record to the trusted resource including the encrypted content and the encrypted private metadata to which the trusted resource has no access.
 2. The computer-implemented system of claim 1, wherein the validation engine is further operative to compare the public metadata to the standard template associated with the content type, and wherein the validation signal is produced as a function of the comparisons to both the private and public metadata.
 3. The computer-implemented system of claim 1, wherein the request module communicates the request to the trusted resource free of transmission of the PRN key over the network.
 4. A computer-implemented system for preparing content having a content type for transmission as an electronic document over a network from a content provider to a managed subscriber having a subscriber ID, comprising: a processor; a content enrichment module operative within the processor to output an enriched content that includes the content, public metadata, and private metadata, wherein the public and private metadata in the enriched content is included in accordance with a standard template associated with the content type and maintained by a trusted resource independent of the content provider; a key generator module operative within the processor to respond to requests with a pseudorandom number (PRN) key; an encryption module operative within the processor, in communication with the key generator module, and further operative to request and receive the PRN key and to encrypt the content and the private metadata using the PRN key; a transaction formatting module operative within the processor in response to any encryption by the encryption module so as to create a record that comprises the encrypted content, the encrypted private metadata, and the public metadata; a request module operative within the processor in response to creation of the record so as to request the trusted resource for an asymmetric key without transmitting the PRN key in the clear to the trusted resource and to include the asymmetric key in the record, wherein the asymmetric key is a public key asymmetric encryption of the PRN key; and a distribution module that distributes the record to the trusted resource including the encrypted content and the encrypted private metadata to which the trusted resource has no access.
 5. The computer-implemented system of claim 4, wherein a validation of the metadata is performed under the control of the content provider.
 6. The computer-implemented system of claim 4, wherein the content comprises video, audio, or both.
 7. The computer-implemented system of claim 4, further comprising a content repository configured to store content in an electronic form, wherein the content encrypted by the encryption module is stored in the content repository.
 8. The computer-implemented system of claim 4, further comprising a memory, wherein the content enrichment module is further operative to determine whether a recipient of the content is a managed subscriber and to add the public and private metadata required by the standard template from the memory.
 9. The computer-implemented system of claim 4, wherein the PRN key comprises a symmetric encryption key for encrypting the content and the private metadata.
 10. The computer-implemented system of claim 4, wherein the system is configured to have the content distributed exclusively by the distribution module and so that the PRN key is only distributed after undergoing the public key asymmetric encryption by the asymmetric key.
 11. The computer-implemented system of claim 4, wherein the request by the request module includes at least one of a Provider GUID and a Subscriber GUID.
 12. The computer-implemented system of claim 4, wherein the request by the request module includes a transaction number suitable for uniquely identifying the request made by the content provider.
 13. The computer-implemented system of claim 4, wherein the request by the request module includes a Provider GUID, a Subscriber GUID, a document type, and a transaction number.
 14. The computer-implemented system of claim 4, wherein the request module communicates the request to the trusted resource free of transmission of the PRN key over the network.
 15. The computer-implemented system of claim 4, wherein the public metadata is communicated over the network from the content provider to the managed subscriber in an unencrypted form.
 16. The computer-implemented system of claim 4, wherein there are a plurality of content types and wherein the public metadata are common to the plural content types.
 17. The computer-implemented system of claim 16, wherein the plurality of content types correspond, at least in part, to a set of private metadata templates associated with a particular industry.
 18. The computer-implemented system of claim 17, further comprising a receipt and management software executing on a machine associated with the managed subscriber, wherein the receipt and management software component is configured to automatically organize and manage the distributed record on the basis of the private metadata in the distributed record.
 19. The computer-implemented system of claim 4, further comprising a receipt and management software executing on a machine associated with the managed subscriber, wherein the receipt and management software component is configured to implement features in response to the public metadata in the distributed record.
 20. The computer-implemented system of claim 19, wherein the features are selected from the group of: addressing, asymmetric encryption, routing, auditing and alerting.
 21. The computer-implemented system of claim 4, wherein the PRN key comprises a symmetric key which is independently generated at each of the content provider and the trusted resource, in synchronization with one another, and wherein the request module is further operative to apply the PRN key generated at the content provider to an asymmetrically encrypted PRN key that was generated at the trusted resource so as to expose the asymmetric key provided by the trusted resource.
 22. The computer-implemented system of claim 21, wherein the asymmetric key provided by the trusted resource is associated with the managed subscriber. 